Skip to content

Unify flyway schemas and fix PostgreSQL v1_12_35#2906

Open
avgustinmm wants to merge 1 commit intoeclipse-hawkbit:masterfrom
boschglobal:unify_flyway_schemas
Open

Unify flyway schemas and fix PostgreSQL v1_12_35#2906
avgustinmm wants to merge 1 commit intoeclipse-hawkbit:masterfrom
boschglobal:unify_flyway_schemas

Conversation

@avgustinmm
Copy link
Contributor

No description provided.

@avgustinmm avgustinmm force-pushed the unify_flyway_schemas branch 6 times, most recently from 4b89a34 to 256af43 Compare February 5, 2026 11:07
Signed-off-by: Avgustin Marinov <Avgustin.Marinov@bosch.com>
@avgustinmm avgustinmm force-pushed the unify_flyway_schemas branch from 256af43 to a063183 Compare February 6, 2026 10:11
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 6, 2026

@@ -1,4 +1,4 @@
ALTER TABLE sp_software_module_type ADD COLUMN min_artifacts integer default 0 NOT NULL;
DROP INDEX sp_idx_distribution_set_01;
DROP INDEX sp_idx_distribution_set_01_sp_distribution_set;
Copy link
Contributor

@vasilchev vasilchev Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this edits intermediate migration - is that even ok ?
what happens if already processed but now it is with different checksum ?

I see two indexes

Create in

POSTGRESQL/V1_12_15__baseline___POSTGRESQL.sql
CREATE INDEX **sp_idx_distribution_set_01_sp_distribution_set** ON sp_distribution_set USING BTREE (tenant, deleted, complete);

RE-CREATE in
POSTGRESQL/V1_12_35__sm_type_min_artifacts__POSTGRESQL.sql
DROP INDEX **sp_idx_distribution_set_01**;
CREATE INDEX **sp_idx_distribution_set_01** ON sp_distribution_set USING BTREE (tenant, deleted);

So maybe in 1_12_35 where it was suppose to drop the one in 1_12_15 and recreate it it actually dropped nothing and just created the new one ? or it was wrong and actually migration would fail because could not find the 'sp_idx_distribution_set_01' and actually this never worked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants